************************************************************************** 
(C) COPYRIGHT International Business Machines Corp. 1994, 1995, 1996, 1997,
1998. All Rights Reserved. Licensed Materials - Property of IBM.
**************************************************************************
FILE: README


**************************************************************

PTF NP00869 (this PTF) applies to the Configuration Program for
2216 routers that have EPTF00L or later installed. Use PTF NP00868
for routers with loads before EPTF00L.

**************************************************************
* PTF NP00869 IS A MANDATORY PTF FOR ALL CUSTOMERS UPGRADING *
* from: 2216 MAS V1R1 *
* to: 2216 MAS V2R1 *
**************************************************************


PTF NP00869 replaces PTF NP00866, NP00887, or NP00868 and
2216 MAS V2R1.

The IBM 2216 Nways Multiprotocol Access Services Configuration Program
Version 2 Release 1 is a replacement for IBM Nways Multiprotocol Access Services
Configuration Program Version 1 Release 1.

The Nways Multiprotocol Access Services Configuration Program User's
Guide is available separately (GC30-3830).

The IBM 2216 Multiprotocol Access Services Configuration Program Version
2R1 (hereby referred to as the Configuration Program) is shipped on 8
diskettes.
- Diskettes 1-6 contain the Configuration Program
- Diskettes 7-8 contain the WIN32S specific programs

Table of Contents:

1. WIN32S(needed for MS-Windows 3.1x)
2. Migration support for downlevel configuration files
3. Installation Files
4. Fonts
5. Initialization Files
6. Problem Determination
7. IBM Xstation Setup
8. Anonymous ftp site for IBM 2216 Multiprotocol Router
9. Using the Configuration Program
10. Restrictions
11. Installing the Configuration Program
12. Hardware and Software Requirements
13. Sending/Retrieving the Configuration file
14. CDB File Locking Enhancement
15. Using the Configuration Program command line
16. ASCII Read function restrictions
17. APARs (problems) fixed in this Configuration Program


1. WIN32S

NOTE: The WIN32S diskettes are only needed for running the Configuration
Program on MS-Windows 3.1x workstations. If you have not already installed
WIN32S, you must do so in order to run the Configuration Program on this
platform.


WIN32S Install Instructions:
1.Stop all Windows applications
2.In Windows Program Manager, select FILE, then RUN...
3.Put diskette 7 of 8 in diskette drive A:
4.In Command Line (of RUN...) enter: A:SETUP and press OK.
5.Note message to add SHARE.EXE to AUTOEXEC.BAT file (SHARE is
part of DOS; the AUTOEXEC.BAT file can be modified after this
install).
6.At next prompt for the WIN32S Setup diskette, insert 8 of 8.
7.Expect message "WIN32S files successfully installed".
8.Optional FREECELL program is on diskette 7 of 8.
9.SETUP will restart WINDOWS to complete the installation.


2. MIGRATION SUPPORT FOR DOWNLEVEL CONFIGURATION FILES

To use configuration files created by earlier versions of
the configuration program, you MUST migrate to the new
release format. If the only copy of the configuration is
either in the router or in binary format, you must use
the version of the configuration program that created the
configuration to create the configuration database file.

Creating Configuration Database File
To create the configuration database file:
1. Start the previous version of the configuration program.
2. Select READ ROUTER CONFIGURATION to read the existing
configuration into the configuration program. Another
way to load an existing configuration into the
program is to select COMMUNICATION, SINGLE, and then
RETRIEVE from the Configuration menu.
3. Select SAVE CONFIGURATION from the File menu.
4. Save the configuration into a file with file extension .CDB.

Converting a Configuration Database File
Configurations already in a configuration database may be
migrated to the new release format by:
1. Starting the current version of the configuration program.
2. Selecting OPEN CONFIGURATION from the File menu.
Select the old configuration from within the .cdb
file you created in "Creating Configuration Database
File." The configuration program will then ask if you
wish to convert the configuration to the new format.
3. Selecting SAVE CONFIGURATION AS to save the configuration
to a new file with a new name. Using the "Save configuration
as" function allows you to keep the existing configuration
file for future use.

Router configuration format(readable by 2216)

If you did not save ".cdb" files using the previous versions of the
Configuration Programs, you should find a copy of the Configuration
Program which matches your router software to create ".cdb" files.
The Configuration Program will check the level of the configuration
at the beginning of a READ ROUTER CONFIGURATION or RETRIEVE, and
terminate the read if the level of the configuration does not match
the level of the Configuration Program.


3. Installation Files

Refer to the "Installing the Configuration Program" section for
instructions on how to install the Configuration Program. When you
install the Configuration Program, several files will be copied to the
installation directory. IT IS CRITICAL THAT YOU HAVE WRITE PERMISSION
TO THE INSTALLATION DIRECTORY TO INSTALL AND USE THE CONFIGURATION
PROGRAM. The Configuration Program writes the program files to the
installation directory during installation. During program execution,
the Configuration Program writes to the installation directory such
information as the font and colors to use in the program. The
Configuration Program also writes files to the installation directory
when creating or reading a configuration and in the event of an
"Internal execution error". Additionally, the Configuration Program
can write files ending with the extensions "cdb" or "mdb" to the
installation directory when saving a configuration or sending multiple
configurations to 2216 routers. These files are in binary format and
should not be changed via a file editor or with an AIX command.

4. Fonts

Font requirements for AIX

The configuration program requires specific X11 fonts.
When the configuration program starts, it looks for the
Helvetica, Times Roman, and New Century Schoolbook fonts
in the /usr/lib/X11/fonts/75dpi directory. The font files
have the following names:

helv*.Z
tim*.Z
ncen*.Z

After the configuration program starts, you can access
any font supported by your system. If you select an
unusual font style, or very large font size, you may lose
the ability to read the panels or make selections from
them. See the following procedures to recover from font problems.

a.Open the directory that contains the Configuration Program and
edit the CFG.INI file. Search for the line that reads
FONTSIZE=xx(where xx is a font size) and change the parameter to
FONTSIZE=14. For AIX systems, search for the line that reads
FONTFAMILY=xxx (where xxx is a font name) and change the parameter to
FONTFAMILY=helvetica. For systems using Windows, change the
parameter to FONTFAMILY=system.

b.For AIX systems, locate the AIX.INI file on the Configuration
Program diskettes. Copy this file to the directory that contains the
Configuration Program and rename the file to CFG.INI. For Windows
systems, locate the WIN31.INI file on the Configuration Program
diskettes. Copy this file to the directory that contains the
Configuration Program and rename the file to CFG.INI.

5. Initialization Files

The Configuration Program uses a user defaults file, cfg.ini, to
perform startup actions while loading the runtime image. Although
this file can be edited manually using a text editor (such as vi), it
is recommended that you make changes to the user defaults file by
using the dialogs Set font, Set Colors and Set default model, found
under the Options item in the Menu bar. The cfg.ini file will be
written when you press the Ok button.

If a cfg.ini file is not in the installation directory, the default
attributes will be used and the cfg.ini file will be re-created using
the defaults.

6. Problem Determination

The file, cfg.err on AIX systems, or CFG.ERR on DOS and OS/2 systems,
is created when an internal execution error occurs in the program.
This file will contain the program stack at the time the error
occurred. The contents of this file should be given to IBM support
when a problem with the Configuration program is reported. The
configuration files in all formats available should also be given to
IBM support to assist with problem determination.

NOTE: The above mentioned file is written to the directory from which
the Configuration Program was started.

7. IBM Xstation Setup

The monitor must have at least 640 x 480 resolution with 16 colors or
grey scales. In order to run the Configuration Program from an IBM
Xstation which is connected to an IBM RISC System/6000 host, you need
to have /usr/lib/X11/fonts/75dpi/ directory in the Font Path of your
Xstation. You can check to see if this directory is already in your
path by typing:

xset -q

Under Font Path, look for /usr/lib/X11/fonts/75dpi/ in the list of
directories.

If you do not have this directory in your Xstation Font Path then from
your Xstation type:

xset fp+ /usr/lib/X11/fonts/75dpi/

This will add the Configuration Program font directory to your
Xstation Font Path. For future use of the Configuration Program
through Xstations, place the above line in your .profile.

NOTE: If your font path is not set correctly, you may get an "out of
memory" error message.

8. Anonymous ftp site and web page for IBM 2216 Configuration Programs

IBM has established an anonymous ftp site for providing information
and configuration program updates (and in the future other program
updates) relating to the 2216.

The hostname for the anonymous ftp site is ftp.nways.raleigh.ibm.com.
If you have trouble resolving this name the IP address is
204.146.167.70. After connecting to the machine specify anonymous as
the user id and your e-mail address as your password. Check the
README file on the anonymous ftp site in the /pub directory for the
latest information.

The subdirectories where the Configuration Prorgrams reside are as
follows:

pub/config/2216/2.2.0/GA/diskettes for the diskette images
for PCs and Risc/6000s

pub/config/2216/2.2.0/GA/runtime for the RISC System/6000 files
(note that runtime files are now in tar.Z format)

There is also a 2216 Configuration program web page for users with web
browsers. The URL is listed below:

http://www.networking.ibm.com/code.nsf/2216code?OpenView


9. Using the Configuration Program

From the Navigation Window, under the Help pulldown, there is a
Tutorial available to help a new user get familiar with using the
Configuration Program. The Tutorial is also available in the
Configuration Window when 'Router' is selected from the Navigation
Window.

This chapter explains how to start and operate the Configuration
Program. This chapter also includes instructions for creating IBM
2216 configuration files and transporting them to the IBM 2216.

-Starting the Configuration Program

The procedure you follow for starting the Configuration Program
depends on whether your workstation is a RISC System/6000 workstation
or a PC workstation.

Starting the Configuration Program on AIX

Before starting the configuration program:
1. X-Windows** must be running on the workstation.
2. The fonts required by the configuration program must
be available. See "Font Requirements for AIX" on
page 9 for the font requirements.
3. /X11fnt.coreX.fnt must be installed to have access to
the MIT X11.5 (75-dp1 and 100-dou) fonts.

To start the configuration program:
1. Enter XINIT to start X-Windows, if not already started.
2. Change the current directory to the directory con-
taining the Configuration Program files, for example CD MAS220.
3. Enter CFG. to display the title window for the configuration
program.


Starting the Configuration Program on OS/2 or DOS/Windows

1. Locate and open the configuration program folder.
2. Double-click on the Configuration Program icon to
start the program. The title window for the configuration
program will be displayed.

10. Restrictions.

This section discusses some KEY considerations that users must be
aware of when creating valid configurations.

-You MUST make sure that TCP/IP is installed and RUNNING before using
the "Communications Single" and/or "Communications Multiple" functions.
On some platforms, the Configuration Program will hang if TCP/IP is
not installed and running.

-ELS (Event Logging System) data
The Configuration Program does not support ELS configurations. Thus,
if you want to configure ELS you must use the online configuration
program on the router. When reading configurations from the router,
the Configuration Program will preserve any ELS configuration done
in the online configuration on the router and send it back on a
subsequent send.

-AIX Version 3.2.5 or 4.1.x is now required for the Config Program.
If you are not sure which version of AIX you have currently, use the
'oslevel' command. The output from the command for an AIX 3.2.5 system
is '>3250'. Some of the earlier versions of AIX do not support the
'oslevel' command.

The Configuration Program is not fully supported on OS/2 WARP 4.0.
Compatibility with OS/2 WARP 4.0 is considered a priority and is
being addressed. There are users that are using the Configuration
Program on OS/2 WARP 4.0, but they are using it at their own risk.

11. Installing the Configuration Program

This chapter provides instructions for installing the Configuration
Program.


-Installation on a RISC System/6000 (requires AIX 3.2.5 or higher)
==================================
To install the Configuration Program on a RISC System/6000
workstation:

STEP 1 Log in to AIX as a non-root user.

STEP 2 Place diskette 1 in the 3.5-inch diskette
drive.

STEP 3 At the AIX prompt, type the following command:

NOTE: AIX is case-sensitive.

dosread -a INSTALL.AIX INSTALL.AIX

Where:

dosread Reads the file from a DOS diskette and places
it in the current directory.

-a Converts the DOS file to an AIX file.

install.aix Is the file name on the diskette.

install.aix Is the file name to be used in the AIX system.

If the install.aix command fails, it may indicate that the
current directory is not part of your search path. To
continue the install, type: ./INSTALL.AIX

STEP 4 Type: chmod 550 INSTALL.AIX

Where:

chmod Changes the file permissions given to the
owner and group.

550 Defines the permission types for a user, group,
and other users. In this case, the user and
group are allowed read and execute permission
and others are allowed only read permission.

install.aix Is the name of the file for which you are
changing the permissions.

STEP 5 At the AIX prompt, type INSTALL.AIX and press ENTER.

STEP 6 Follow the prompts that appear on the screen to complete
the installation.


-Installation on a PC
====================
Using OS/2

To install the Configuration Program on a PC workstation running
OS/2 2.1 or 3.0, follow these steps:

STEP 1 Place diskette 1 in the diskette drive.

STEP 2 At the OS/2 prompt, type A:OS2INST and press ENTER.

STEP 3 Follow the prompts that appear on the screen.

The Configuration Program will install itself on the system and will
prompt you to enter the installation drive and directory. An IBM 2216
folder will be created with the Configuration Program icon inside.

NOTE: See the Restrictions section regarding OS/2 WARP 4.0


Using Windows

To install the Configuration Program on a PC work-station running
Windows, type WIN A:INSTALL beside the DOS prompt or follow these
steps:

Windows 95 Instructions

STEP 1 Start Windows 95
STEP 2 Place diskette 1 in the diskette drive.
STEP 3 Double click on the MyComputer icon.
STEP 4 Double click on the 3 1/2 Floppy[A:] icon.
STEP 5 Double click on the Install.exe icon.
STEP 6 Follow the prompts that appear on the screen.

Windows 3.1x Instructions

NOTE: If you have not installed the WIN32s diskettes (required for
Windows 3.1x only), you must do so BEFORE installing the Configuration
Program.

STEP 1 Start Windows.
STEP 2 Place diskette 1 in the diskette drive.
STEP 3 Select FILE from the menu bar.
STEP 4 Select RUN from the pull-down window.
STEP 5 Type A:INSTALL on the command line and select OK to start
the installation.
STEP 6 Follow the prompts that appear on the screen.


The Configuration Program will install itself on the system disk drive
and will prompt you to enter the installation directory, group box
name, and any other details necessary to complete the installation.

After a successful installation, an icon labeled 'MAS V2R2 Config'
will be added to the program group you specify using the installation
program or, by default, to the IBM 2216 program group. In addition,
an icon is now provided for the README file as well.

NOTE: In subsequent installations, the settings for the exiting icon
for the current release will be changed to reflect the new installation
and working directories.

To delete one of the icons, follow these steps:

Windows 95 Instructions

STEP 1 Single left mouse click on Start icon.
STEP 2 Move mouse pointer over Settings.
STEP 3 Single left click on Taskbar.
STEP 4 Single left click on Start Menu Programs.
STEP 5 Single left click on Remove.
STEP 6 Single left click on the + icon beside IBM 2216 to expand.
STEP 7 Single left click on MAS V2.0 Config.
STEP 8 Single left click on Remove.

Windows 3.1x Instructions

STEP 1 Select the icon that you want to delete.
STEP 2 Select FILE from the menu bar.
STEP 3 Select DELETE from the cascade menu.
STEP 4 An information message window is displayed. Select YES to
delete the icon.

Files copied during installation

When you install the Configuration Program on a RISC System/6000 or
PC workstation, a number of files are copied to the installation
directory. The installation directory will be named mrsc110 by
default. If you have deleted the icon in the steps above and would
like to complete the clean up, you should also delete the files in
the installation directory. The files that are copied vary according
to the type of workstation you are using. If you want to change the
name of the installation directory, provide the name you prefer
before installing the Configuration Program files.


12. Hardware and Software requirements

Hardware and Software requirements for the RISC System/6000

The following hardware and software are required to run the
Configuration Program on the RISC System/6000 work-station:

-IBM AIX 3.2.5 or higher with Transmission Control Protocol/Internet
Protocol (TCP/IP) enabled

-IBM AIXwindows*
-16 MB of memory (32 MB recommended)
-3.5-inch diskette drive that can read and write 1.44-MB formatted
diskettes
-14 MB of available space on the fixed disk drive
-A graphics display that supports 640*480 resolution and 16 colors
or gray scales (1024*768 resolution and 256 colors recommended)
-A mouse

Hardware and Software requirements for the PC

The following hardware and software are required to use the
Configuration Program on a PC workstation using an Intel** 80386**
or higher processor or a compatible system that has an Intel 80386 or
higher processor (486 DX2-50 is the minimum recommended processor).

For workstations running the Microsoft** Windows** program, you need:

-IBM DOS 5.0 or higher, MS-DOS 5.0 or higher
-Microsoft Windows 3.1 or later versions
o Win32s, included with the MRNS Configuration Program diskettes
Not needed by Windows 95
o WinSock 2.0 DLL (included with Win32s)
-TCP/IP application that uses WinSock 2.0
(This is only required for using the Communications functions)
-16 MB of memory (32 MB recommended)
-3.5-inch diskette drive that can read and write 1.44 MB-formatted
diskettes
-14 MB of available space on the fixed disk drive
-A graphics display that supports 640*480 resolution or higher and 16
colors or gray scales (1024*768 resolution and 256 colors recommended)
-A mouse
-If you encounter problems with windows not updating properly, ensure
that you have installed the latest BIOS and video drivers provided
by the manufacturer.


For workstations running the IBM Operating System/2 (OS/2) program,
you need:

-OS/2 2.1 or WARP 3.0, see Restrictions about OS/2 WARP 4.0
-IBM TCP/IP 1.2.1 for OS/2 or later (This is only required for using
the Communications functions)
-16 MB of memory (32 MB recommended)
-3.5-inch diskette drive that can read and write 1.44-MB formatted
diskettes
-14 MB of available space on the fixed disk drive
-10 MB of available swapper disk space on the swapper fixed disk
drive partition
-A graphics display that supports 640*480 resolution or higher and 16
colors or gray scales (1024*768 resolution and 256 colors recommended)
-A mouse
-If you encounter problems with windows not updating properly, ensure
that you have installed the latest BIOS and video drivers provided by
the manufacturer.


13. Sending/Retrieving the Configuration file

Note: It helps to step through the Configuration Program as you read
this.

You MUST make sure that TCP/IP is installed and RUNNING before using
the "Communications Single" and/or "Communications Multiple" functions.

The Communications function will communicate with the router using
the SNMP protocol. The router must be set up with an IP Address and
have a SNMP community with access defined as WRITE_READ_TRAP for send and
restart. For retrieve and query, the community access can be READ_TRAP or
WRITE_READ_TRAP.

The single send will send the configuration that is currently open. The
IP destination and community fields will default to what is defined in
the configuration. The timeout value is the maximum number of seconds
the send function will wait for a response. Select the appropriate
action(s):
1. Send the configuration to the router
2. Restart the router immediately or later
3. Send the configuration and then restart the router
4. Query the router for the System Description.
5. Retrieve the configuration from the router.

Query will get the system description from the router and display
the IP Address, version/release, system name, contact, location,
and up time. The four Communications functions are mutually exclusive
with the exception of Send and Restart, which can be used together.

The multiple send/retrieve will act on configurations that are saved in
the configuration database. The send lists (.mdb files) contain groups of
configuration names and parameters to be sent/retrieved. For each
configuration the parameters are: IP destination, community,
timeout, send, restart, date, time, query, and retrieve. For each entry,
the configuration can be sent, the router can be restarted immediately,
the configuration can be sent and the router restarted at a
later time, or the router can be queried for its System Description.
The configurations can also be retrieved from several routers into one
or more configuration databases.

To create a send list, type in the Send list name. Select the
'Show .cdb' button. Choose the database and configuration and select
the OK button. Select close to exit this screen. The IP destination
and community are initialized from the configuration's values. Any of
the fields can be edited. The field sizes can be changed by 'grabbing'
one of the bars in the header and dragging it left or right. The Send
and Restart functions are selected by default if you create a .mdb
entry in this manner.

The Add button will add an empty row at the bottom of the list.
The delete button will delete any selected row. The Save button will
save the configurations and their parameters into the send list.
If any row is selected, the new row (from Add or Show .cdb) will be
added after the selected row.

The Copy list button will copy the selected send list to a new send
list. The Delete list button will delete the selected send list. The
OK button will start the sending of configurations.

If 'Stop on error' is selected and an error occurs when sending a
configuration, an error message is displayed and all sending stops.
If it is not selected and an error occurs, the error message is
written in the file 'cfg.com' and the sending continues with the
next configuration.

If the router is queried and 'Stop on error' is selected, the
router's information is displayed and all sending/querying stops.
If the router is queried and 'Stop on Error' is not selected, the
system description is written in the file 'cfg.com' and the
sending/querying continues with the next configuration.

For single router restart, the time initializes to the current time
so the router will restart immediately. However the 'Date' and 'Time'
fields can be changed to any date and time. For multiple router
restart, the dates and times initialize to the last entered dates
and times for each row in the selected send list.

The 'All' button will apply the date and time specified in the
'Restart at' area to each row in the list. The 'Selected' button
will only apply the date and time specified in the 'Restart at'
area to the row selected. The date and time fields in the table may
also be directly edited. If the Restart box is selected for a row
and the date and time field are empty, the date and time will
default to the date and time in the 'Restart at' area.

Note: If the restart is sent to the router with a date and time
earlier than the current date and time on the workstation (for
example yesterday's date), the router will be restarted immediately.

The delayed restart time is sent to the router in the form of seconds
(xx). The router will restart at xx seconds from when he receives
the packet (within a two minute window). Therefore if there are many
hops to the destination or the network traffic is heavy, the router
may restart later than expected.

If a timeout error occurs, check that:
1. the IP Destination address is correct
2. there is a route to the IP address
3. the community exists
4. the timeout value is large enough

If an error with the SNMP packet occurs, check that:
1. the community has WRITE_READ_TRAP access
2. for multiple send, the configuration exists in the database


14. CDB File Locking Enhancement

A feature has been added to the config tool that locks the
config database (*.cdb) files while they are being accessed.
If two instances of the config tool write to the same
database at the same time, there was potential for the
database to be corrupted. With the new locking mechanism, a
tool trying to access the file will know when another tool
is already accessing it and wait for the file to become
available.

How it works

When the config tool reads or writes from a .cdb file, it
will add a lock entry to the lock file (creating a new lock
file if necessary). The lock file will have the same name
as the .cdb file, but with a .lok extension (ie ~/test.cdb
will have a lock file named ~/test.lok).

There are two types of lock entries: ReadLock and WriteLock.
It is ok for several tools to have a ReadLock on the same
.cdb file at the same time. The only times that a lock will
be denied are when a WriteLock is requested while a lock (read
or write) already exists on the file, or when a ReadLock is
requested while a WriteLock already exists on the file. This
prevents the case of two tools writing to the same file at
the same time, resulting in corruption.

The lock entry that is placed in the .lok file consists of
the lock type (ReadLock or WriteLock) and the person who
owns that lock. On UNIX platforms, the user@hostname will
be placed in the lockfile. On Windows or OS/2, the contents
of the environment variable 'CFGUSER' will be placed in the
lockfile. The locking mechanism will still work if the
CFGUSER environment variable is not set, but you will not be
able to tell who has the file locked. One good reason to
set CFGUSER, is if a machine goes down while the config tool
is accessing a .cdb file, the lock will remain in place and
must be removed from the file by hand (or by erasing the
.lok file). It will be easy to verify if the lock is
invalid if you know who owns the lock.

Setting the CFGUSER environment variable

UNIX users need not worry about this step as user@hostname
replaces this information.

From any Windows or OS/2 command line execute the following:

set CFGUSER=<your text here>

This command can also be placed in your AUTOEXEC.BAT file on
Windows, or CONFIG.SYS file on OS/2 so it is set every time
your machine boots.


15.Using the Configuration Program command line

The command line options are listed from within the
Configuration Program under Help->On commands... from the
main menu bar. These arguments can be listed as parameters after
the command to invoke the Configuration Program, or put into
the default command line argument file 'cfgargs'. The 'cfgargs'
file will be read and executed if it exists, and then erased,
so keep a copy. The user may also put command line arguments
into a file of his choice and read them using the command line
argument '-commandsFrom userFile'.

There are a couple of command line restrictions that should be
noted. One is that the user cannot use * directly from the
command line. If the user wants to use a *, they must use it
from the cfgargs or other arguments file.

Another has to do with invoking the Configuration Program from
an AIX shell script. If the user wanted to update a parameter
on multiple routers in one command, he might create one argument
file with a series of -retrieve and -asciiWrite lines, one pair
per router. Then the user would create another argument file of
a different name with a series of -asciiRead and -send lines,
again one pair per router with the ascii file names and router
IP addresses matching those of the first argument file. When
the Configuration Program is invoked from an AIX shell script
it will look something like the following:

cfg.aix cfg.app -commandsFrom argumentFile1
anotherScriptWhichDoesStreamEditingToChangeTheParameterForEachRouter
cfg.aix cfg.app -commandsFrom argumentFile2

The restriction is that if you were to try to use 'cfg -batch'
instead of the 'cfg.aix cfg.app', then the Configuration
Program would be started in the background and both the script
which does the stream editing(sed or awk) and the second
invocation of the Configuration Program would fail because the
ascii files would not exist yet.

16.ASCII Read function restrictions

The Configuration Program will only read ASCII files created with
the same version of the Configuration Program. Upgrade of
configurations from release to release must be done using the
.cdb format.

The Configuration Program User's Guide has a section 'Reading
Partial Configuration Files'. Do not do step 2, which says,
'Using a text editor, remove all groups that you are not changing.'
Currently, there are problems reading a partial configuration file.


17.APARs (problems) fixed in this Configuration Program

2216 MAS V2R1 PTF NP00869 4 June 1998
-------------------------

THIS IS A MANDATORY PTF FOR ALL CUSTOMERS UPGRADING
from: 2216 MAS V1R1
to: 2216 MAS V2R1

PTF NP00869 replaces all previous PTFs (NP00866, NP00867, and
NP00868) and contains all fixes made in those previous PTFs.

PTF NP00866 contained fixes for the following 3 APARs
-----------------------------------------------------
NA03288 CONFIGURATOR OPEN AND SAVE PERFORMANCE VERY SLOW
NA03375 CONFIGURATOR CDB FILE GROWS TOO LARGE
NA03429 CONFIG COMMAND LINE FACILITY STOPS UNTIL MOUSE IS MOVED

PTF NP00867 FIX SUMMARY
=======================
The following is a summary list of APARs fixed in this PTF.
A detailed abstract follows this summary list.

NA03271
NA03324
*NA03330
NA03353
NA03358
NA03369
NA03419
@NA03428
NA03431
NA03441
NA03443
NA03467
NA03489
NA03563
NA03564
NA03568
NA03574
NA03581
NA03622
NA03649
NA03668

* Fixed in PTF NP00866
@ Fixed on Web and CDroms: GA diskettes were bad.
_________________________________________________________________________

DETAILED ABSTRACTS
-------------------------------------------------------------------------
NA03271 THE DEFAULT FOR RPS SHOULD BE NO SO THAT IT DOESN'T INTERFERE WITH LNM.
The default for RPS has been set to "off".
To find this parameter, select a Token Ring interface. Under Bridging,
select Interfaces, and then Configure under the Token Ring.
Select the LNM tab. RPS is the last parameter on the screen.
-------------------------------------------------------------------------
NA03324 CONFIG. TOOL SHOULD NOT ACCEPT THE SDLC LINK POLL DELAY IN INCREMENTS
OF LESS THAN 0.1 SECONDS DUE TO PERFORMANCE REASONS.
The link poll delay now always rounds up to the nearest 100 milliseconds
(nearest 0.1 seconds). EG if 350 m-sec input, the value is set
to 400 m-sec (0.4 seconds). A 320 m-sec input yields 300 m-sec
(0.3 seconds).
-------------------------------------------------------------------------
NA03330 WHEN USER DEFINES SECOND MULTI-LINK, GETS ERROR.
The second entry attempt gets an error that the 1st one is already
defined. The user has to make a trivial change to make the second
definition unique.
------------
This problem was fixed in the PTF NP00866 for 2216 MAS V2R1, and
therefore is fixed in this PTF.
-------------------------------------------------------------------------
NA03353 WHEN 1.1 CONFIG TOOL READS A CONFIG FROM THE ROUTER IT TRUNCATES A
6 BYTE ZERO MAC ADDRESS TO A 1 BYTE MAC ADDRESS.
When opening a config cdb, generated by config tool 791, the
model type is incorrect. A 24T can be read in as a 24M and
vice-versa. Also Fields Router, Devices, and Interfaces have
question marks.
------------
When you see a "?", select this line and click the middle (AIX)
mouse button for validation and error explanation.
-------------------------------------------------------------------------
NA03358 CANNOT ENTER MORE THAN 14 DIGITS IN DTE ADDRESS FIELD, X.25
Under APPN folder: Interface panel: Link Stations button: General 2 tab:
Enter any DTE address longer than 14 characters produces message:
"AXCE003, Internal execution error. Subscript out of bounds." When
the configuration is sent to the router or saved as a configuration
file.
-------------------------------------------------------------------------
NA03369 CONFIG TOOL DISPLAYS ERROR ACXE0003 AFTER READING SAVED FILE.
After reading in an ASCII configuration file (previously created
with the config tool) back into the Config Tool, an error
message is received: "ACXE0003 Internal execution error. Attempt
to index a non-existent element."
Error occurs after write, read ASCII file, and then going to
'local X.25 DTE addresses'.
-------------------------------------------------------------------------
NA03419 CONFIG TOOL DOES NOT MATCH TALK 6 TOKEN RING MTU RANGE AND GRANULARITY.
Currently the Configuration Tool allows only certain values for
the Token Ring interface MTU size. The Token Ring MTU size must
be adjustable down to the byte level to correspond to the Talk 6
way of setting the MTU size.
-------------------------------------------------------------------------
NA03428 ERROR ACXE003 MESSAGE WHEN CONFIGURING INTERFACE FOR FRAME RELAY.
When user is creating new configuration for a 24M he selects the
interfaces panel under General, and then selects the first WAN
interface to change it to Frame Relay (default is PPP). After
selecting Frame Relay in the drop-down menu, the user gets the
error message: "ACXE0003 Internal execution error. Message not
understood."
-------------------------------------------------------------------------
NA03431 CREATE ROUTER CONFIG IS NOT POSSIBLE AS SOON AS A NETBIOS NAME
FILTER IS DEFINED.
This problem exists in 2210 MRS V2R1 and 2216 MAS V2R1, and
occurs only if ISDN is used. This error does NOT occur in
2210 MRS V2R2 and 2216 MAS V2R2.
-------------------------------------------------------------------------
NA03441 TAKES OVER 2 MINUTES TO CONVERT ASCII TO BINARY FILE VIA AIX MACHINE.
The batch facility is used to convert ASCII configuration data
to binary on an AIX platform. This conversion takes approximately
2 minutes which is too long for multiple conversions.
------------
This performance problem has been maximized (improved) in the PTF's:
2216 MAS V1R1 NP00851
2216 MAS V2R1 NP00866
2216 MAS V2R2 NP00886
and therefore is fixed in this PTF.
Further performance improvements can be obtained by running the
configuration on faster workstations.
-------------------------------------------------------------------------
NA03443 IT LOOKS THE CONFIG PGM DOES NOT HANDLE THE SAPS FOR DLSW ESCON
INTERFACES CORRECTLY. THEY ARE GETTING LOST WHEN SAVING THE FILE.
The SAPs for DLSW ESCON interfaces are getting lost when saving
the file in 2216 MAS V1R1.
-------------------------------------------------------------------------
NA03467 WINDOWLESS FOR MAS GETS IMPROPER TIME OF DAY.
Using windowless Configuration Tool with "cfgargs" and the batch
commands, the cfgargs specify that the router should reload at
a specific time. When the batch command is invoked, the log
contains time stamps five hours earlier than the workstation and
the 2216 time. Both the workstation and the 2216 are using CUT
(GMT) time. Result: the router is reloaded 5 hours later than
required.
-------------------------------------------------------------------------
NA03489 CANNOT ENTER SDLC GROUP POLL ADDRESS IN 2216
In the 2216 Configuration Tool, it is not possible to enter a
Group Poll Address. The field is found under Devices, Interfaces,
SDLC, Configure, Detail. Group poll address is grayed out,
whether Role is Primary, Secondary, or Negotiable.
-------------------------------------------------------------------------
NA03563 MAS 2.2 TOOL ABENDS AFTER UPGRADE OF 1.1 CONFIG
When you read a MAS 1.1 config .cdb file into a MAS 2.2 Config
Tool, the initial read in appears ok, if you attempt to change
an adapter in some slot to no adapter, the 2.2 tool abends.
-------------------------------------------------------------------------
NA03564 MAS V2.2 TOOL REQUIRES 12 0'S FOR UNIVERSAL MAC ADDRESS
When reading a MAS v1r1 config into a MAS v2.2 tool, question
marks show up on the token ring adapter configs, the tool is
requiring 12 0's to specify the use of the Universally
Administered mac address. Only one 0 was needed in v1r1.
-------------------------------------------------------------------------
NA03568 CONFIG TOOL 2.1, INTER EXEC ERROR MSG: NOT UNDERSTOOD:# ASNUMBER
If "Other Connection Network" in APPN folder is switched ON,
reading back the configuration from the 2210 stops with
"Internal execution error message: not understood: # asNumber".
The same error occurs when reading back a saved configuration
from workstation disk. Problem found on both AIX and Windows95.
-------------------------------------------------------------------------
NA03574 USER CANNOT SPECIFY PRIMARY IP ADDR ON INTERFACE
2216 Configuration Tool does not allow specifying the primary
IP address for an interface. Instead, it configures the
numerically largest address configured on the interface. This
needs to be fixed especially for DHCP.
-------------------------------------------------------------------------
NA03581 CONFIGURATOR ORDERS ISDN ADDRESSES NUMERICALLY
When configuring ISDN addresses under Router, Devices, General,
ISDN Addresses. The Configuration Tool sorts the addresses by
ISDN address name and by Network Dial Address (number). There
are more than one possible Network Dial Address (numbers) for
the same ISDN address name, and one of them is the long distance
number (starts with 1). The long distance number is always
called first, which is not what is wanted. Needs to sort only
by ISDN address name.
-------------------------------------------------------------------------
NA03622 X.25 STANDARDS MISSING FROM CFG TOOL PANEL
Missing fields were returned to panels.
-------------------------------------------------------------------------
NA03649 ACXE0003 INT. EXEC. ERROR: MESSAGE NOT UNDERSTOOD: #SPEC
When upgrading from V2R1 to V2R2 via the Configuration Tool,
the error message was received: "ACXE0003 Internal execution
error: Message not understood: #spec" when trying to configure
CIP over ATM.
-------------------------------------------------------------------------
NA03668 SOME OF THE APPN CONFIGURATIONS ARE WIPED OUT WHEN MIGRATE THE
CONFIGURATION FILE FROM V2R1 TO V2R2 CONFIGURATION TOOL.
Some of the APPN configuration data is lost when migrating a
configuration from V2R1 to V2R2. The missing data has to be
re-entered manually.

PTF NP00868Fix Summary
=======================

The following APARs are fixed in this PTF:


NA03369  CONFIG TOOL DISPLAYS ERROR ACXE0003 AFTER READING SAVED FILE.   
NA03788  APPN ON MPC+ ESCON TG CHARS EFFECTIVE CAPACITY DEFAULT TOO LOW          
         When upgrading config to NP00863 (V2.1) customer gets ACXE0069

PTF NP00869 Fix Summary
=======================

NA03464  APPN CONFIG TOOL RTP INACTIVITY TIMER NEEDS TO BE IN SECONDS

    Note: NA03464 requires the 2216 to have EPTF00L or later code installed.
